Hi,

We recently introduced a Exchange 2010 server into our Exchange 2003 enviroment but had to stop migrating users over to it after it became appartent that users using Outlook 2010 could not switch on their Out Of Office, getting an "Your automatic reply settings cannot be displayed because the server is currently unavailable" error. However users on the new 2010 can set OOF if they use OWA or Outlook 2003!

Running the Test E-mail AutoConfiguration shows no errors with the Log tab showing Autodiscover succeeded and the Results tab showing all the correct values, including a OOF URL of /Autodiscover/Autodiscover.xml">https://<servername>/Autodiscover/Autodiscover.xml into IE gives a XML file with a 600 error code.

I have looked at loads of 'solutions' on the Internet but cannot get this working, anyone have any suggestions?

Thank you,

Craig

Code 600 -- it is an expexcted result which means the autodiscover can be accessed without issue.

Please verify name resolution and proxy first in client and check if the link below would help you.

http://social.technet.microsoft.com/Forums/sk/exchange2010/thread/42834f9a-14fa-49dc-b345-9f974af09063

And detail the extact steps your had tried would save our time of troubleshooting. Thanks.

Tony Chen

TechNet Community Support

Hi,

What exactly do you mean by 'name resolution'?  I am able to ping the server by name and also access OWA, etc from the client.  I can also access the URL's used for EWS and AutoDiscover from the client.

• I ran the Test Email AutoConfiguration which is successful.
• I can connect to the OOF and AutoDiscover URLs in IE correctly.
• I have tried adding an DNS record for AutoDiscover and also added a SRV record for it too.
• I have tried adding the server name to the IE proxy exception list and also added it to the Local Intranet sites list in the IE Security section.
• I have tried updating/patching the Outlook client, and ran a repair on it.
• I have deleted the Outlook profile and re-created it (both using AutoDiscover and Manually).
• I have tried Anonymous Authentication both enabled and disabled on EWS in IIS.
• I created a brand new test account directly on the Exchange 2010 server (other accounts were moved from Exchange 2003) and got the same result.

When searching the Internet for the error message, a lot of the problems seem to be issues with AutoDiscover, but I believe that is working fine in our case.  It is weird that OOF on the same account doesn't work on Outlook 2010 but does with Outlook 2003 and OWA!

Craig

Are these clients connecting via RPC or via HTTP?
Hold CTRL and right on the Outlook icon in the Notification Area and choose Connection Status...

Then, lookup the configured URLs for the corresponding connection via the same right click trick and then choosing Test E-mail AutoConfiguration (only select "Use AutoDiscover").

Unless you are using split-DNS, usually Exchange RPC is configured with the internal names and Exchange HTTP with the external names. When internal clients also connect via Exchange HTTP, split-DNS is required.

That it works for Outlook 2003 is logical since that uses Public Folders and not the EWS to set the OOF.

Hi,

All clients are connecting via RPC, we do not use RPF over HTTP at all.

I can access all the URLs from the Test Email AutoConfiguration report in a web browser.

Craig

Please verify IIS settings:

======================

• On Exchange CAS server, open IIS console,
• Go to default web site, double click SSL Settings,  make sure Client Certificates is set to Ignore
• Click Autodiscover, double click SSL Settings,  make sure Client Certificates is set to Ignore
• Click EWS, double click SSL Settings,  make sure Client Certificates is set to Ignore
• Click OAB, double click SSL Settings,  make sure Client Certificates is set to Ignore
• Please run IISRESET command to load the changes.

Thanks.

Tony Chen

TechNet Community Support

All IIS settings were already set as per the ost above, but still does not work.

Regards,

Craig

Hey Craig

Try this it worked for me :)

http://thoughts.stuart-edwards.info/index.php/sysadmin/exchange-2010/your-automatic-reply-settings-cannot-be-displayed-because-the-server-is-currently-unavailable

Good luck

Randall

Thanks Randall, but I have tried that already... and it still doesn't work :-(

Craig

Did you by chance go down this road...? Ensuring you have the necessary SRV record in your external DNS zone?

http://support.microsoft.com/kb/940881

Use the following parameters to create a new SRV record (if it's not there):

Service: _autodiscover
Protocol: _tcp
Port Number: 443
Host: mail.contoso.com

Sounds like you're successfully using autodiscover though, yet still seeing the error. This one fixed my problems for a user external to my network, connecting in via VPN, who was getting that same error.

My environment is a 2003 Small Business Server / Exchange environment migrated to Exchange 2010, full AD, and I had to create this record in my environment. -Hope it helps.

Go to a client in and unbind the IPV6 in network settings. If everything else is working and you have exhausted all other troubleshooting steps try unchecking that box and it should start working.

Patrick

I fixed a few of my users using a very similar method, I disabled IPv6 on nontunnel interfaces using MS Article ID: 929852 .  My question is should this be used as a solution, or does it help identify what the problem really is. 

Outlook error is one of the  general problem among Outlook user that stops  user to gain complete access over data stored  in pst file. Although Outlook facilitate their user with its inbuilt utility as scanpst.exe  , but most of time especially in severe case it fails to do so, resulting in error. In this situation it is good to opt to  automatic pst repair tool  that has been made specially for the purpose of recovery missing or corrupted pst file

http://msoutlookpstrepair.webnode.com/

I can confirm that this worked for us also.

After messing around with several of the solutions proposed above to no effect, I cleared encryption between Outlook and Exchange, and then set it again - and the problem went away.  It only takes a few seconds to try, and it might just work for you too.....

I can confirm that disabled IPv6 worked for me as well.  thanks!

Have you tried launchin Outlook with the following switches?

For Office 2010, Click Start-RUN and type:

"c:\program files\microsoft office\office14\outlook.exe" /cleanrules

Or /cleanserverrules

/cleanclientrules